Summary

Prevent Cost Insights rollup transactions from outliving their tracked request lifecycle and creating prolonged database lock convoys.

Why this change is needed

Concurrent AI Gateway rollup writes serialize on one owner-hour unique-index entry. Detached post-commit transactions could finish SQL without reaching commit or rollback before serverless execution ended, retaining locks while queued writers consumed database connections.

How this is addressed

• Attach organization usage and Cost Insights follow-up transactions to the existing tracked usage promise while preserving separation from the billing transaction.
• Bound best-effort Cost Insights capture with transaction-local lock, statement, and idle-transaction timeouts without inline retries.
• Keep optional failures from failing canonical usage recording and report only privacy-safe PostgreSQL error metadata.
• Expand hot-key concurrency, lock-timeout, lifecycle, and canonical-repair regression coverage.

Human Verification

• Awaited post-commit lifecycle helper smoke check passed.
• Five-focus code review found no logic, data safety, security, resource, or type-contract issues.

Reviewer Notes

Human Reviewer Flags

• Cost Insights capture remains post-commit and best-effort; timed-out deltas remain repairable from canonical microdollar_usage but do not create a durable dirty-owner marker.
• Full batched derivation is intentionally deferred pending post-fix contention measurements.

Code Reviewer Agent